Skip to content

Align Dependabot coverage and add the dev-fast build fragment - #434

Draft
leynos wants to merge 2 commits into
mainfrom
parabellum-wave-1
Draft

Align Dependabot coverage and add the dev-fast build fragment#434
leynos wants to merge 2 commits into
mainfrom
parabellum-wave-1

Conversation

@leynos

@leynos leynos commented Aug 13, 2026

Copy link
Copy Markdown
Owner

Summary

This branch applies Wave 1 of the Rust estate baseline remediation
(Operation Parabellum, phase 2). It aligns
.github/dependabot.yml
with the canonical Dependabot reference: one update stanza per package
ecosystem the repository uses (cargo, rust-toolchain, github-actions), each stanza labelled
dependencies plus its channel label, and GitHub Actions updates batched
into a single pull request via a wildcard group. It also adds the opt-in dev-fast build
fragment with dev-build and dev-test Make targets, signposted in
AGENTS.md.

Review walkthrough

Validation

  • Audited the amended tree with the Concordat rule packages
    dependabot-baseline and rust-dev-fast-baseline: dependabot-baseline compliant, rust-dev-fast-baseline compliant.

Notes

  • The canonical labels (including the Dependabot channel labels this
    configuration references) were created on the repository ahead of this
    pull request, so no stanza names a missing label.
  • The dev-fast fragment is strictly opt-in local tooling: it is only
    applied when passed explicitly with --config, so continuous
    integration, release, coverage, and verification builds are untouched.
    The targets need a nightly toolchain and, on Linux, a mold binary on
    the PATH; repositories still pinned to stable gain the wiring now and
    the capability when Wave 2 moves the pin to nightly.

Summary by Sourcery

Align Dependabot configuration with Rust toolchain updates and introduce an opt-in fast development build workflow.

New Features:

  • Add dev-build and dev-test Make targets for accelerated local debug builds using an opt-in Cargo config fragment.
  • Provide a canonical dev-fast Cargo configuration fragment enabling Cranelift and mold for development builds.
  • Document fast development build usage and constraints in AGENTS.md.

Enhancements:

  • Extend Dependabot coverage to track rust-toolchain updates with appropriate labels and weekly scheduling.

Bring `.github/dependabot.yml` to the estate baseline: one update
stanza per package ecosystem the repository uses, each labelled
`dependencies` plus its channel label, with GitHub Actions updates
batched into a single pull request via a wildcard group.

Add the opt-in dev-fast build fragment at
`tools/dev-fast/config.toml` (Cranelift codegen for the dev profile
and the mold linker on Linux) with `dev-build` and `dev-test` Make
targets that pass it explicitly via `--config`, and signpost the
workflow in `AGENTS.md`. Release, coverage, and verification builds
are unaffected: the fragment is never auto-discovered.
@coderabbitai

coderabbitai Bot commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: dde5dbb7-8efa-4a70-9019-742e5d480ae2

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Comment @coderabbitai help to get the list of available commands.

@sourcery-ai

sourcery-ai Bot commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Reviewer's Guide

Updates Dependabot configuration to align with canonical Rust estate coverage and introduces an opt-in dev-fast build configuration with Make targets and documentation signposting.

Sequence diagram for the opt-in dev-fast build process

sequenceDiagram
  actor Developer
  participant Makefile
  participant Cargo
  participant DevFastConfigToml

  Developer->>Makefile: make dev-build
  Makefile->>Cargo: cargo --config DEV_FAST_CONFIG build
  Cargo->>DevFastConfigToml: load tools/dev-fast/config.toml
  DevFastConfigToml-->>Cargo: [unstable] codegen-backend, [profile.dev] cranelift
  alt [target_os = "linux"]
    DevFastConfigToml-->>Cargo: [target.'cfg(target_os = "linux")'] rustflags -fuse-ld=mold
  end
  Cargo-->>Developer: dev debug binaries built with Cranelift (mold on Linux)

  Developer->>Makefile: make dev-test
  Makefile->>Cargo: cargo --config DEV_FAST_CONFIG test
  Cargo->>DevFastConfigToml: apply same dev-fast settings for tests
  Cargo-->>Developer: tests run with Cranelift (mold on Linux)
Loading

File-Level Changes

Change Details Files
Add opt-in accelerated debug build and test targets wired to a dev-fast Cargo config fragment.
  • Define DEV_FAST_CONFIG variable defaulting to tools/dev-fast/config.toml.
  • Add phony dev-build and dev-test Make targets invoking cargo with --config $(DEV_FAST_CONFIG) for build and test.
  • Create tools/dev-fast/config.toml with Cranelift dev profile and mold linker configuration gated behind Linux target cfg.
  • Document nightly toolchain and mold requirements, and warn against applying dev-fast config globally via .cargo/config.toml in AGENTS.md.
Makefile
tools/dev-fast/config.toml
AGENTS.md
Extend Dependabot coverage to the rust-toolchain ecosystem with canonical labeling.
  • Add a rust-toolchain update stanza targeting repository root directory.
  • Apply dependencies and rust-toolchain labels to the new stanza to match canonical channel labeling.
  • Schedule rust-toolchain updates to run weekly in Dependabot configuration.
.github/dependabot.yml

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Estate review flagged two defects in the fragment's deployed
comments: a stale "copy this fragment" instruction that reads as
nonsense once the file is in place, and a mis-statement of Cargo's
rustflags semantics (Cargo joins the entries of every matching
`[target.*]` table; only the joined result takes precedence over
`[build].rustflags` rather than merging). Both are corrected in the
canonical source; take its bytes verbatim. No configuration key
changes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant